-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add warning when using a textual date field specifier with the COMPAT locale provider #112548
Conversation
Pinging @elastic/es-core-infra (Team:Core/Infra) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💚 Backport successful
|
… locale provider (elastic#112548) Some textual field specifiers change between COMPAT and CLDR, depending on locale
|
||
// check for all textual fields, and localized zone offset | ||
private static final Predicate<String> CONTAINS_CHANGING_TEXT_SPECIFIERS = System.getProperty("java.locale.providers", "") | ||
.contains("COMPAT") ? Pattern.compile("[EcGaO]|MMM|LLL|eee|ccc|QQQ|ZZZZ").asPredicate() : Predicates.never(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are plenty of integration ingest pipelines that instantiate date
and date_index_name
processors that match this regex.
Is there a way to mitigate the impact for them and reduce the noise from deprecation logs?
Warn users if they're using a textual specifier that might change with CLDR - we can't do a full deprecation cycle, but this will help